SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Backbone network</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Backbone network</span></span>

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">This article is about the general concept. For the Cold War British network called "Backbone", see <a href="British_Telecom_microwave_network" title="British Telecom microwave network">British Telecom microwave network</a>.</div>

</p>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1246091330">

/* start https://en.wikipedia.org/ */

.mw-parser-output .sidebar{width:22em;float:right;clear:right;margin:0.5em 0 1em 1em;background:var(--background-color-neutral-subtle,#f8f9fa);border:1px solid var(--border-color-base,#a2a9b1);padding:0.2em;text-align:center;line-height:1.4em;font-size:88%;border-collapse:collapse;display:table}body.skin-minerva .mw-parser-output .sidebar{display:table!important;float:right!important;margin:0.5em 0 1em 1em!important}.mw-parser-output .sidebar-subgroup{width:100%;margin:0;border-spacing:0}.mw-parser-output .sidebar-left{float:left;clear:left;margin:0.5em 1em 1em 0}.mw-parser-output .sidebar-none{float:none;clear:both;margin:0.5em 1em 1em 0}.mw-parser-output .sidebar-outer-title{padding:0 0.4em 0.2em;font-size:125%;line-height:1.2em;font-weight:bold}.mw-parser-output .sidebar-top-image{padding:0.4em}.mw-parser-output .sidebar-top-caption,.mw-parser-output .sidebar-pretitle-with-top-image,.mw-parser-output .sidebar-caption{padding:0.2em 0.4em 0;line-height:1.2em}.mw-parser-output .sidebar-pretitle{padding:0.4em 0.4em 0;line-height:1.2em}.mw-parser-output .sidebar-title,.mw-parser-output .sidebar-title-with-pretitle{padding:0.2em 0.8em;font-size:145%;line-height:1.2em}.mw-parser-output .sidebar-title-with-pretitle{padding:0.1em 0.4em}.mw-parser-output .sidebar-image{padding:0.2em 0.4em 0.4em}.mw-parser-output .sidebar-heading{padding:0.1em 0.4em}.mw-parser-output .sidebar-content{padding:0 0.5em 0.4em}.mw-parser-output .sidebar-content-with-subgroup{padding:0.1em 0.4em 0.2em}.mw-parser-output .sidebar-above,.mw-parser-output .sidebar-below{padding:0.3em 0.8em;font-weight:bold}.mw-parser-output .sidebar-collapse .sidebar-above,.mw-parser-output .sidebar-collapse .sidebar-below{border-top:1px solid #aaa;border-bottom:1px solid #aaa}.mw-parser-output .sidebar-navbar{text-align:right;font-size:115%;padding:0 0.4em 0.4em}.mw-parser-output .sidebar-list-title{padding:0 0.4em;text-align:left;font-weight:bold;line-height:1.6em;font-size:105%}.mw-parser-output .sidebar-list-title-c{padding:0 0.4em;text-align:center;margin:0 3.3em}@media(max-width:640px){body.mediawiki .mw-parser-output .sidebar{width:100%!important;clear:both;float:none!important;margin-left:0!important;margin-right:0!important}}body.skin--responsive .mw-parser-output .sidebar a>img{max-width:none!important}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-list-title,html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle{background:transparent!important}html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle a{color:var(--color-progressive)!important}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-list-title,html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle{background:transparent!important}html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle a{color:var(--color-progressive)!important}}@media print{body.ns-0 .mw-parser-output .sidebar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><table class="sidebar nomobile nowraplinks"><tbody><tr><th class="sidebar-title" style="background:#ccccff;font-size: 120%"><a href="Computer_network" title="Computer network">Computer network</a> types<br>by scale</th></tr><tr><td class="sidebar-image"><span typeof="mw:File"></span></td></tr><tr><td class="sidebar-content" style="text-align: left">

<ul><li><a href="Nanonetwork" title="Nanonetwork">Nanonetwork</a></li>

<li><a href="Near-field_communication" title="Near-field communication">Near-field (NFC)</a></li>

<li><a href="Personal_area_network" title="Personal area network">Personal (PAN)</a></li>

<li><a href="Local_area_network" title="Local area network">Local (LAN)</a>

<ul><li><a href="Storage_area_network" title="Storage area network">Storage (SAN)</a></li>

<li><a href="Wireless_LAN" title="Wireless LAN">Wireless (WLAN)</a></li>

<li><a href="VLAN" title="VLAN">Virtual (VLAN)</a></li>

<li><a href="Campus_network" title="Campus network">Campus (CAN)</a></li>

<li><a href="Metropolitan_area_network" title="Metropolitan area network">Metropolitan (MAN)</a>

<ul><li><a href="Municipal_wireless_network" title="Municipal wireless network">Municipal wireless (MWN)</a></li></ul></li>

<li><a href="Internet_area_network" title="Internet area network">Cloud</a></li>

<li><a href="Internet" title="Internet">Internet</a></li>

<li><a href="Interplanetary_Internet" title="Interplanetary Internet">Interplanetary Internet</a></li></ul></td>

</tr><tr><td class="sidebar-navbar"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></td></tr></tbody></table>

<p>A <b>backbone</b> or <b>core network</b> is a part of a <a href="Computer_network" title="Computer network">computer network</a> which interconnects networks, providing a path for the exchange of information between different <a href="LAN" class="mw-redirect" title="LAN">LANs</a> or <a href="Subnetwork" class="mw-redirect" title="Subnetwork">subnetworks</a>.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> A backbone can tie together diverse networks in the same building, in different buildings in a campus environment, or over wide areas. Normally, the backbone's capacity is greater than the networks connected to it.<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup>

</p><p>A large corporation that has many locations may have a backbone network that ties all of the locations together, for example, if a server cluster needs to be accessed by different departments of a company that are located at different geographical locations. The pieces of the network connections (for example: Ethernet, wireless) that bring these departments together is often mentioned as network backbone. <a href="Network_congestion" title="Network congestion">Network congestion</a> is often taken into consideration while designing backbones.<sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup>

</p><p>One example of a backbone network is the <a href="Internet_backbone" title="Internet backbone">Internet backbone</a>.<sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

<p>The theory, design principles, and first instantiation of the backbone network came from the telephone core network when traffic was purely voice. The <i>core network</i> was the central part of a <a href="Telecommunications_network" title="Telecommunications network">telecommunications network</a> that provided various <a href="Service_(systems_architecture)" title="Service (systems architecture)">services</a> to customers who were connected by the <a href="Access_network" title="Access network">access network</a>. One of the main functions was to <a href="Routing_in_the_PSTN" title="Routing in the PSTN">route telephone calls</a> across the <a href="PSTN" class="mw-redirect" title="PSTN">PSTN</a>.

</p><p>Typically the term referred to the high capacity communication facilities that connect primary nodes. A core network provided paths for the exchange of information between different <a href="Sub-network" class="mw-redirect" title="Sub-network">sub-networks</a>.

</p><p>In the United States, <a href="Local_exchange" class="mw-redirect" title="Local exchange">local exchange</a> core networks were linked by several competing <a href="Interexchange_carrier" title="Interexchange carrier">interexchange networks</a>; in the rest of the world, the core network has been extended to national boundaries.

</p><p>Core networks usually had a <a href="Mesh_topology" class="mw-redirect" title="Mesh topology">mesh topology</a> that provided any-to-any connections among devices on the network. Many main service providers would have their own core/backbone networks that are interconnected. Some large enterprises have their own core/backbone network, which are typically connected to the public networks.

</p><p>Backbone networks create links that allow long-distance transmission, usually 10 to 100 miles, and in certain cases - up to 150 miles. This makes backbone network essential to providing long-haul <a href="Wireless" title="Wireless">wireless</a> solutions to provide <a href="Internet_protocol_suite" title="Internet protocol suite">internet service</a>, especially to remote areas.<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Functions">Functions</h2></div>

<p>Core networks typically provided the following functionality:

</p>

<ol><li>Aggregation: The highest level of aggregation in a service provider network. The next level in the hierarchy under the core nodes is the distribution networks and then the edge networks. <a href="Customer-premises_equipment" title="Customer-premises equipment">Customer-premises equipment</a> (CPE) do not normally connect to the core networks of a large service provider.</li>

<li><a href="Authentication" title="Authentication">Authentication</a>: The function to decide whether the user requesting a service from the telecom network is authorized to do so within this network or not.</li>

<li>Call control and switching: <a href="Call_control" title="Call control">call control</a> or <a href="Telephone_exchange" title="Telephone exchange">switching</a> functionality decides the future course of call based on the call signaling processing. E.g. switching functionality may decide based on the "<a href="Called_party" title="Called party">called number</a>" that the call be routed towards a <a href="Subscriber" class="mw-redirect" title="Subscriber">subscriber</a> within this operator's network or with <a href="Local_number_portability" title="Local number portability">number portability</a> more prevalent to another operator's network.</li>

<li>Charging: This functionality of the collation and processing of charging data generated by various network nodes. Two common types of charging mechanisms found in present-day networks are prepaid charging and postpaid charging. <i>See <a href="Automatic_Message_Accounting" class="mw-redirect" title="Automatic Message Accounting">Automatic Message Accounting</a></i></li>

<li>Service invocation: The core network performs the task of service invocation for its subscribers. Service invocation may happen based on some explicit action (e.g. <a href="Call_transfer" title="Call transfer">call transfer</a>) by user or implicitly (<a href="Call_waiting" title="Call waiting">call waiting</a>). It's important to note however that service execution may or may not be a core network functionality as third-party networks and nodes may take part in actual service execution.</li>

<li><a href="Gateway_(telecommunications)" title="Gateway (telecommunications)">Gateways</a>: Gateways shall be present in the core network to access other networks. Gateway functionality is dependent on the type of network it interfaces with.</li></ol>

<p>Physically, one or more of these logical functionalities may simultaneously exist in a given core network node.

</p><p>Besides the above-mentioned functionalities, the following also formed part of a telecommunications core network:

</p>

<ul><li>O&M: <a href="Network_operations_center" title="Network operations center">Network operations center</a> and <a href="Operations_support_system" title="Operations support system">operations support systems</a> to configure and provision the core network nodes. Number of subscribers, <a href="Peak_hour" class="mw-redirect" title="Peak hour">peak hour</a> call rate, nature of services, geographical preferences are some of the factors that impact the configuration. Network statistics collection, alarm monitoring and logging of various network nodes actions also happens in the O&M center. These stats, alarms and traces form important tools for a network operator to monitor the network health and performance and improvise on the same.</li>

<li>Subscriber database: The core network also hosts the subscriber database (e.g. HLR in GSM systems). The subscriber database is accessed by core network nodes for functions like authentication, profiling, service invocation etc.</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Distributed_backbone">Distributed backbone</h2></div>

<p>A distributed backbone is a backbone network that consists of a number of connectivity devices connected to a series of central connectivity devices, such as hubs, switches, or routers, in a hierarchy.<sup id="cite_ref-Cengage1_7-0" class="reference"><a href="#cite_note-Cengage1-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> This kind of topology allows for simple expansion and limited capital outlay for growth, because more layers of devices can be added to existing layers.<sup id="cite_ref-Cengage1_7-1" class="reference"><a href="#cite_note-Cengage1-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> In a distributed backbone network, all of the devices that access the backbone share the transmission media, as every device connected to this network is sent all transmissions placed on that network.<sup id="cite_ref-BICSI1_8-0" class="reference"><a href="#cite_note-BICSI1-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup>

</p><p>Distributed backbones, in all practicality, are in use by all large-scale networks.<sup id="cite_ref-Dooley_9-0" class="reference"><a href="#cite_note-Dooley-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup> Applications in enterprise-wide scenarios confined to a single building are also practical, as certain connectivity devices can be assigned to certain floors or departments.<sup id="cite_ref-Cengage1_7-2" class="reference"><a href="#cite_note-Cengage1-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> Each floor or department possesses a <a href="LAN" class="mw-redirect" title="LAN">LAN</a> and a wiring closet with that workgroup's main hub or <a href="Router_(computing)" title="Router (computing)">router</a> connected to a bus-style network using backbone cabling.<sup id="cite_ref-TNE_10-0" class="reference"><a href="#cite_note-TNE-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup> Another advantage of using a distributed backbone is the ability for network administrator to segregate workgroups for ease of management.<sup id="cite_ref-Cengage1_7-3" class="reference"><a href="#cite_note-Cengage1-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup>

</p><p>There is the possibility of single points of failure, referring to connectivity devices high in the series hierarchy.<sup id="cite_ref-Cengage1_7-4" class="reference"><a href="#cite_note-Cengage1-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> The distributed backbone must be designed to separate network traffic circulating on each individual LAN from the backbone network traffic by using access devices such as routers and bridges.<sup id="cite_ref-11" class="reference"><a href="#cite_note-11"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Collapsed_backbone">Collapsed backbone</h2></div>

<p>A conventional backbone network spans distance to provide <a href="Interconnectivity" class="mw-redirect" title="Interconnectivity">interconnectivity</a> across multiple locations. In most cases, the backbones are the links while the switching or <a href="Routing" title="Routing">routing</a> functions are done by the equipment at each location. It is a distributed architecture.

</p><p>A collapsed backbone (also known as inverted backbone or backbone-in-a-box) is a type of backbone network architecture. In the case of a collapsed backbone, each location features a link back to a central location to be connected to the collapsed backbone. The collapsed backbone can be a cluster or a single switch or router. The topology and architecture of a collapsed backbone is a <a href="Star_network" title="Star network">star</a> or a <a href="Rooted_tree" class="mw-redirect" title="Rooted tree">rooted tree</a>.

</p><p>The main advantages of the collapsed backbone approach are

</p>

<ol><li>ease of management since the backbone is in a single location and in a single box, and</li>

<li>since the backbone is essentially the back plane or internal switching matrix of the box, proprietary, <a href="High_performance_technology" class="mw-redirect" title="High performance technology">high performance technology</a> can be used.</li></ol>

<p>However, the drawback of the collapsed backbone is that if the box housing the backbone is down or there are <a href="Reachability" title="Reachability">reachability</a> problem to the central location, the entire network will crash. These problems can be minimized by having <a href="Redundancy_(engineering)" title="Redundancy (engineering)">redundant</a> backbone boxes as well as having secondary/backup backbone locations.

</p>

<div class="mw-heading mw-heading2"><h2 id="Parallel_backbone">Parallel backbone</h2></div>

<p>There are a few different types of backbones that are used for an enterprise-wide network. When organizations are looking for a very strong and trustworthy backbone they should choose a parallel backbone. This backbone is a variation of a collapsed backbone in that it uses a central <a href="Node_(networking)" title="Node (networking)">node</a> (connection point). Although, with a parallel backbone, it allows for duplicate connections when there is more than one <a href="Router_(computing)" title="Router (computing)">router</a> or <a href="Network_switch" title="Network switch">switch</a>. Each switch and router are connected by two cables. By having more than one cable connecting each device, it ensures network connectivity to any area of the enterprise-wide network.<sup id="cite_ref-Network_12-0" class="reference"><a href="#cite_note-Network-12"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup>

</p><p>Parallel backbones are more expensive than other backbone networks because they require more cabling than the other <a href="Network_topologies" class="mw-redirect" title="Network topologies">network topologies</a>. Although this can be a major factor when deciding which enterprise-wide topology to use, the expense of it makes up for the efficiency it creates by adding increased performance and <a href="Fault_tolerance" title="Fault tolerance">fault tolerance</a>. Most organizations use parallel backbones when there are critical devices on the network. For example, if there is important data, such as <a href="Payroll" title="Payroll">payroll</a>, that should be accessed at all times by multiple departments, then your organization should choose to implement a parallel backbone to make sure that the connectivity is never lost.<sup id="cite_ref-Network_12-1" class="reference"><a href="#cite_note-Network-12"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Serial_backbone">Serial backbone</h2></div>

<p>A serial backbone is the simplest kind of backbone network.<sup id="cite_ref-13" class="reference"><a href="#cite_note-13"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup> Serial backbones consist of two or more internet working devices connected to each other by a single cable in a daisy-chain fashion. A daisy chain is a group of connectivity devices linked together in a serial fashion. Hubs are often connected in this way to extend a network. However, hubs are not the only device that can be connected in a serial backbone. <a href="Gateway_(telecommunications)" title="Gateway (telecommunications)">Gateways</a>, <a href="Router_(computing)" title="Router (computing)">routers</a>, <a href="Switch" title="Switch">switches</a> and <a href="Network_bridge" title="Network bridge">bridges</a> more commonly form part of the backbone.<sup id="cite_ref-14" class="reference"><a href="#cite_note-14"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup> The serial backbone topology could be used for enterprise-wide networks, though it is rarely implemented for that purpose.<sup id="cite_ref-15" class="reference"><a href="#cite_note-15"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup>

</p>

<ul><li><a href="Backhaul_(telecommunications)" title="Backhaul (telecommunications)">Backhaul</a></li>

<li><a href="Core_router" title="Core router">Core router</a></li>

<li><a href="Network_service_provider" title="Network service provider">Network service provider</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://searchsmb.techtarget.com/sDefinition/0,,sid44_gci211629,00.html">"What is a Backbone?"</a>. <i>Whatis.com</i>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20080516035653/http://searchsmb.techtarget.com/sDefinition/0,,sid44_gci211629,00.html">Archived</a> from the original on May 16, 2008<span class="reference-accessdate">. Retrieved <span class="nowrap">June 25,</span> 2007</span>.</cite></span>

</li>

<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.angelfire.com/ut/cnst/Chap8.html">"Backbone Networks"</a>. <i>Chapter 8</i>. Angelfire. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200728173151/http://www.angelfire.com/ut/cnst/Chap8.html">Archived</a> from the original on 28 July 2020<span class="reference-accessdate">. Retrieved <span class="nowrap">2 October</span> 2013</span>.</cite></span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text"><cite id="CITEREFTurner2007" class="citation web cs1">Turner, Brough (12 September 2007). <a rel="nofollow" class="external text" href="http://www.circleid.com/posts/congestion_backbone_telecom_internet/">"Congestion in the Backbone: Telecom and Internet Solutions"</a>. CircleID. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200218181016/http://www.circleid.com/posts/congestion_backbone_telecom_internet/">Archived</a> from the original on 18 February 2020<span class="reference-accessdate">. Retrieved <span class="nowrap">2 October</span> 2013</span>.</cite></span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text"><cite id="CITEREFKashyapSun,_FangtingShayman,_Mark" class="citation web cs1">Kashyap, Abhishek; Sun, Fangting; Shayman, Mark. <a rel="nofollow" class="external text" href="http://www.ee.umd.edu/~shayman/papers.d/wcnc_2006_congestion.pdf">"Relay Placement for Minimizing Congestion in Wireless Backbone Networks"</a> <span class="cs1-format">(PDF)</span>. Department of Electrical and Computer Engineering, University of Maryland. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20131005015940/http://www.ee.umd.edu/~shayman/papers.d/wcnc_2006_congestion.pdf">Archived</a> <span class="cs1-format">(PDF)</span> from the original on 5 October 2013<span class="reference-accessdate">. Retrieved <span class="nowrap">2 October</span> 2013</span>.</cite></span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><cite id="CITEREFHowdie2013" class="citation web cs1">Howdie, Ben (28 January 2013). <a rel="nofollow" class="external text" href="http://www.kashflow.com/blog/the-backbones-connected-to-the/">"The Backbone's connected to the…"</a>. KashFlow. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20131005005637/http://www.kashflow.com/blog/the-backbones-connected-to-the/">Archived</a> from the original on 5 October 2013<span class="reference-accessdate">. Retrieved <span class="nowrap">2 October</span> 2013</span>.</cite></span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><cite id="CITEREFNetworks" class="citation web cs1">Networks, Ceragon. <a rel="nofollow" class="external text" href="https://www.ceragon.com/what-is-5g-wireless-backhaul">"What is 5G Wireless Backhaul"</a>. <i>www.ceragon.com</i>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20220520193327/https://www.ceragon.com/what-is-5g-wireless-backhaul">Archived</a> from the original on 2022-05-20<span class="reference-accessdate">. Retrieved <span class="nowrap">2022-05-09</span></span>.</cite></span>

</li>

<li id="cite_note-Cengage1-7"><span class="mw-cite-backlink">^ <a href="#cite_ref-Cengage1_7-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Cengage1_7-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-Cengage1_7-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-Cengage1_7-3"><sup><i><b>d</b></i></sup></a> <a href="#cite_ref-Cengage1_7-4"><sup><i><b>e</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFDean2010" class="citation book cs1">Dean, Tamara (2010). <i>Network+ Guide to Networks 5th Edition</i>. Boston, MA: Cengage Course Technology. p. 202. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1423902454</bdi>.</cite></span>

</li>

<li id="cite_note-BICSI1-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-BICSI1_8-0">^</a></b></span> <span class="reference-text"><cite class="citation book cs1">"Distributed backbone network". <a rel="nofollow" class="external text" href="http://etidweb.tamu.edu/cdrom3/CHAPTER8.PDF"><i>BICSI Lan Design Manual</i></a> <span class="cs1-format">(PDF)</span>. 1996. p. 20. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20110719124820/http://etidweb.tamu.edu/cdrom3/CHAPTER8.PDF">Archived</a> <span class="cs1-format">(PDF)</span> from the original on July 19, 2011<span class="reference-accessdate">. Retrieved <span class="nowrap">May 7,</span> 2011</span>.</cite></span>

</li>

<li id="cite_note-Dooley-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-Dooley_9-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFDooley2002" class="citation web cs1">Dooley, Kevin (January 1, 2002). <a rel="nofollow" class="external text" href="https://www.scribd.com/doc/54296513/8/Distributed-Backbone">"Designing Large-Scale Networks"</a>. <i>O'Reilly Online Catalog</i>. p. 23. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20121107103626/http://www.scribd.com/doc/54296513/8/Distributed-Backbone">Archived</a> from the original on November 7, 2012<span class="reference-accessdate">. Retrieved <span class="nowrap">May 7,</span> 2011</span>.</cite></span>

</li>

<li id="cite_note-TNE-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-TNE_10-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.thenetworkencyclopedia.com/d2.asp?ref=193">"Distributed Backbone"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20111009121228/http://www.thenetworkencyclopedia.com/d2.asp?ref=193">Archived</a> from the original on October 9, 2011<span class="reference-accessdate">. Retrieved <span class="nowrap">May 7,</span> 2011</span>.</cite></span>

</li>

<li id="cite_note-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-11">^</a></b></span> <span class="reference-text"><cite id="CITEREFBoon_&_Kepekci1996" class="citation book cs1">Boon & Kepekci (1996). <i>BICSI Lan Design Manual</i>. Tampa, FL. pp. <span class="nowrap">20–</span>21.</cite><span class="cs1-maint citation-comment"><code class="cs1-code">{{cite book}}</code>: CS1 maint: location missing publisher (link)</span></span>

</li>

<li id="cite_note-Network-12"><span class="mw-cite-backlink">^ <a href="#cite_ref-Network_12-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Network_12-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFDean2010" class="citation book cs1">Dean, Tamara (2010). <i>Network+ Guide to Networks 5th Edition</i>. Boston, MA: Cengage Course Technology. pp. <span class="nowrap">203–</span>204. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1423902454</bdi>.</cite></span>

</li>

<li id="cite_note-13"><span class="mw-cite-backlink"><b><a href="#cite_ref-13">^</a></b></span> <span class="reference-text">CompTIA Network+ In depth, Chapter 5 p. 169</span>

</li>

<li id="cite_note-14"><span class="mw-cite-backlink"><b><a href="#cite_ref-14">^</a></b></span> <span class="reference-text"><cite id="CITEREFDean2010" class="citation book cs1">Dean, Tamara (2010). <i>Network+ Guide to Networks 5th Edition</i>. Boston, MA: Cengage Course Technology. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1423902454</bdi>.</cite></span>

</li>

<li id="cite_note-15"><span class="mw-cite-backlink"><b><a href="#cite_ref-15">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20060718163853/http://www.angelfire.com/mech/phattony/enterprise.htm">"Backbone Networks"</a>. Archived from <a rel="nofollow" class="external text" href="http://www.angelfire.com/mech/phattony/enterprise.htm">the original</a> on 2006-07-18.</cite></span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20181028124233/http://ipv6.nlsde.buaa.edu.cn/">IPv6 Backbone Network Topology</a></li></ul></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2024-08-18" href="https://en.wikipedia.org/wiki/?title=Backbone_network&oldid=1240978417">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>